Adding directives for JavaScript files directly into source code in a multi-tenant database environment

ABSTRACT

In a method, system, and computer-readable medium having instructions for adding directives for JavaScript files directly into source code, a source file for preprocessing is received and the source file is written in a client-side scripting language, the source file is parsed, directive information is identified within the source file, metadata is associated with the directive during preprocessing, metadata associated is retrieved with a preprocessed directive, a request to access metadata associated with a preprocessed directive in the source file is received and the preprocessed directive is the directive from the source file, and at least a portion of markup language is generated for a web page in accordance with metadata associated with the preprocessed directive in response to the request.

CLAIM OF PRIORITY

This application claims the benefit of U.S. Provisional patentapplication 61/349,132 entitled “METHODS AND SYSTEMS FOR ADDINGDIRECTIVES FOR JAVASCRIPT FILES DIRECTLY INTO SOURCE CODE IN AMULTI-TENANT DATABASE ENVIRONMENT” by Mooney, filed May 27, 2010, theentire contents of which are incorporated herein by reference.

CROSS REFERENCE TO RELATED APPLICATIONS

The following commonly owned, co-pending United States Patents andPatent Applications, including the present application, are related toeach other. Each of the other patents/applications is incorporated byreference herein in its entirety, including: U.S. patent applicationSer. No. 12/985,298, entitled “ADDING DIRECTIVES FOR VERSIONS OFJAVASCRIPT FILES DIRECTLY INTO SOURCE CODE IN A MULTI-TENANT DATABASEENVIRONMENT,” by Mooney, filed Jan. 5, 2011.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent file or records, but otherwise reserves all copyrightrights whatsoever.

FIELD OF THE INVENTION

One or more implementations relate generally to adding directives forJavaScript files directly into source code.

BACKGROUND

The subject matter discussed in the background section should not beassumed to be prior art merely as a result of its mention in thebackground section. Similarly, a problem mentioned in the backgroundsection or associated with the subject matter of the background sectionshould not be assumed to have been previously recognized in the priorart. The subject matter in the background section merely representsdifferent approaches, which in and of themselves may also be inventions.

In conventional database systems, users access their data resources inone logical database. A user of such a conventional system typicallyretrieves data from and stores data on the system using the user's ownsystems. A user system might remotely access one of a plurality ofserver systems that might in turn access the database system. Dataretrieval from the system might include the issuance of a query from theuser system to the database system. The database system might processthe request for information received in the query and send to the usersystem information relevant to the request on a webpage. The rapid andefficient retrieval of accurate information and subsequent delivery ofthis information to the user system has been and continues to be a goalof administrators of database systems.

Oracle Corporation JavaScript™ (hereinafter JavaScript) is a programminglanguage and/or scripting language that may be used with a web browserat the client-side (e.g. user system) to provide enhanced userinterfaces and dynamic websites. Approaches to delivering JavaScript tothe client-side include sending all of JavaScript for the website toclient for every page delivered which may unnecessarily slow thedelivery of information because all of the JavaScript may not be used onthe webpage. Unfortunately, conventional database approaches mightbecome inefficient if, for example, all of the JavaScript for a websiteis sent to the client for each webpage when a fraction of the JavaScriptis utilized on the webpage.

Accordingly, it is desirable to provide techniques enabling a way todeliver JavaScript more efficiently to the user of the database system,and/or to improve efficiency of the database system.

BRIEF SUMMARY

In accordance with embodiments, there are provided mechanisms andmethods for adding directives for JavaScript files directly into sourcecode.

In a method, system, and computer-readable medium having instructionsfor adding directives for JavaScript files directly into source code, asource file for preprocessing is received and the source file is writtenin a client-side scripting language, the source file is parsed,directive information is identified within the source file, metadata isassociated with the directive during preprocessing, metadata associatedis retrieved with a preprocessed directive, a request to access metadataassociated with a preprocessed directive in the source file is receivedand the preprocessed directive is the directive from the source file,and at least a portion of markup language is generated for a web page inaccordance with metadata associated with the preprocessed directive inresponse to the request.

While one or more implementations and techniques are described withreference to an embodiment in which adding directives for JavaScriptfiles directly into source code is implemented in a system having anapplication server providing a front end for an on-demand databaseservice capable of supporting multiple tenants, the one or moreimplementations and techniques are not limited to multi-tenant databasesnor deployment on application servers. Embodiments may be practicedusing other database architectures, i.e., ORACLE®, DB2® by IBM and thelike without departing from the scope of the embodiments claimed.

Any of the above embodiments may be used alone or together with oneanother in any combination. The one or more implementations encompassedwithin this specification may also include embodiments that are onlypartially mentioned or alluded to or are not mentioned or alluded to atall in this brief summary or in the abstract. Although variousembodiments may have been motivated by various deficiencies with theprior art, which may be discussed or alluded to in one or more places inthe specification, the embodiments do not necessarily address any ofthese deficiencies. In other words, different embodiments may addressdifferent deficiencies that may be discussed in the specification. Someembodiments may only partially address some deficiencies or just onedeficiency that may be discussed in the specification, and someembodiments may not address any of these deficiencies.

BRIEF DESCRIPTION OF THE DRAWINGS

In the following drawings like reference numbers are used to refer tolike elements. Although the following figures depict various examples ofthe invention, the invention is not limited to the examples depicted inthe figures.

FIG. 1 illustrates an example of a simplified flow diagram for animplementation of adding directives for JavaScript files directly intosource code;

FIG. 2 illustrates an example of a simplified flow diagram for animplementation of adding directives for JavaScript files directly intosource code;

FIG. 3 illustrates an example of a block diagram for an implementationof adding directives for JavaScript files directly into source code;

FIG. 4 illustrates an example of a flow diagram for an implementation ofadding directives for JavaScript files directly into source code;

FIG. 5 illustrates a block diagram of an example of an environmentwherein an on-demand database service might be used; and

FIG. 6 illustrates a block diagram of an embodiment of elements of FIG.5 and various possible interconnections between these elements.

DETAILED DESCRIPTION General Overview

Systems, computer readable mediums, and methods are provided for addingdirectives for JavaScript files directly into source code. In one ormore embodiments, a configurable directive may be placed directly insource code to provide direction for the generation of one or moreversions of the source code. Source code is a collection of declarationsand/or statements written in a computer programming language, such asJavaScript. The configurable directive may be configured to indicate amode, a portion of a markup language to place in a webpage, associatemetadata with the directive and/or source code file, and/or a portion ofthe JavaScript to place in the JavaScript file for the mode. Theoriginal JavaScript source code file may be preprocessed to generate oneor more versions of JavaScript with or without the portion of theJavaScript as designated in the directive. Preprocessing is processingdata that may be input to another program and/or process. Preprocessingof a JavaScript source code file with directives in one or moreembodiments may enable the generation of a version of a JavaScript filefor each mode in the original source code file.

The mode may indicate a type or a version of the original JavaScriptsource code file that contains the JavaScript specified in theconfigurable directive. It may be desirable to break up and group theJavaScript in accordance with the expected usage of the JavaScript in aparticular version to efficiently deliver the appropriate JavaScript fora webpage. In one or more embodiments, the modes may be used to groupJavaScript files that are expected to be used by a particular userand/or a particular purpose. For example, a version of a JavaScript fordebugging may have debugging code in the JavaScript whereas the versionof JavaScript for production may be compressed and not as easilyreadable for debugging purposes.

In another example, the JavaScript may be grouped in accordance with theusage on particular webpages. For example, JavaScript that is used on amajority of webpages for a website may be grouped together in oneJavaScript file and included with a majority of the webpages. JavaScriptused for fewer pages may be grouped in accordance with the expectedusage on a webpage and included on relatively fewer webpages.

The JavaScript files may be embedded or included in HyperText MarkupLanguage (HTML) files. HTML is a set of markup tags and the tags areused to describe web pages. JavaScript is a client-side scriptinglanguage and may be used to enable access to data and/or objects withina host and/or client-side environment. JavaScript may be downloaded tothe client device or user system from the server and executed locally atthe client. JavaScript may be viewed as a prototype-basedobject-oriented scripting language that may not use classes and behaviorreuse may be accomplished with cloning of objects. The JavaScript may becompiled and/or interpreted with a web browser at the client andexecuted locally at the client. A web browser is a software applicationfor retrieving, presenting, and traversing information resourcesavailable on the World Wide Web and/or over a network. Those with skillin the art will recognize that there are various compilers and/orbrowsers that may be used to implement adding directives for JavaScriptfiles directly into source code. Although implementations are providedthroughout that add directives to JavaScript files, those with skill inthe art will recognize that implementations may add directives to sourcecode for a variety of client-side scripting languages. For example,directives may be added to Adobe Actionscript™ source code files.

Embodiments may use directives in the source code to associate metadatato a particular JavaScript file(s) and/or the configurable directive inthe JavaScript. The metadata may be identified or generated duringpreprocessing of the directive. The metadata may be stored for laterretrieval and/or kept in memory after preprocessing of the JavaScriptfile(s) for later retrieval. The associated metadata for a preprocesseddirective may be retrieved when the source code is compiled and executedat a client device using the web browser. The web server is a softwareapplication that helps to deliver content that can be accessed throughthe internet or over a network with the web browser. In one or moreembodiments, a script is run by the web server to ensure that themetadata associated with a preprocessed directive is in memory andavailable for retrieval.

As used herein, the term multi-tenant database system refers to thosesystems in which various elements of hardware and software of thedatabase system may be shared by one or more customers. For example, agiven application server may simultaneously process requests for a greatnumber of customers, and a given database table may store rows for apotentially much greater number of customers. As used herein, the termquery plan refers to a set of steps used to access information in adatabase system.

Next, systems and methods for adding directives for JavaScript filesdirectly into source code will be described with reference to exampleembodiments. FIG. 1 illustrates an example of a simplified flow diagramfor an implementation of adding directives for JavaScript files directlyinto source code. A JavaScript source file for preprocessing may bereceived (100). A script may be created to indicate the JavaScript filesthat may need preprocessing and execute a process for the preprocessingof the files. In one or more embodiments, a script may designate a rootdirectory for the source files, a file to start parsing from, thedirectives recognized by a group, and/or the modes used forpreprocessing. For example, a Java™ class file may be created with amethod to run the preprocessing for one or more JavaScript files in aparticular directory. In another example, the preprocessing andgeneration of versions of source code for the JavaScript may beperformed during a build process with a build tool, such as duringApache Ant™ task. A build process may entail compiling software intoexecutable code and running a script to preprocess the JavaScript files.

The preprocessor may be a software program that processes its input datato produce output that is used as input to another program or process.The use of a JavaScript preprocessor may enable a user to put directiveswith metadata for JavaScript files directly into the source code forpreprocessing. The directives may indicate a version of a JavaScriptsource code file to generate and the JavaScript to include in theresulting preprocessed JavaScript version of the JavaScript source codefile. The resulting preprocessed JavaScript files may be used on one ormore webpages served to a client device.

The JavaScript source file may be parsed (102). The preprocessor mayparse the JavaScript source code file to identify one or more directivesand any information for the directive. Parsing may entail the process ofanalyzing text to identify tokens (e.g. words and expressions) andidentifying grammatical structures in the JavaScript in accordance witha provided grammar. Those with skill in the art will recognize that avariety of parsing tools may be used to perform lexical analysis,syntactic analysis, and/or semantic analysis to parse the JavaScriptsource code file.

Directive information for a directive may be identified within theJavaScript source file (104). The directive may be configured by theuser and directive information for the directive may be provided withthe directive in the JavaScript source code file. The directiveinformation may be any textual data, numerical data, or any combinationthereof that can be provided with the directive and parsed. For example,the directive may have directive information associated with thedirective, such as data on at least a portion of a JavaScript file and amode. The data on at least a portion of a JavaScript file may be a filepath, a directory path, a relative file path, or any other data thatdesignates a location for a portion and/or one or more files. Theportion of the JavaScript file may constitute an entire file forJavaScript, one or more files, and/or it may have what constitutes aportion of JavaScript file (e.g. half of a function in JavaScript).

The directive may indicate that the portion of JavaScript file includedwith the directive be placed in the version of the JavaScript file wherethe directive is found in the original JavaScript source code file. Inanother embodiment, the directive may indicate a relative position inthe JavaScript source code file for placement of at least the portion ofthe JavaScript file. For example, the directive may indicate theordering of placement of JavaScript files found in a directory to beplaced in the version of the JavaScript file. Continuing with theexample, a directory may have files A.js, B.js, and C.js, and thedirective may indicate the ordering of the placement of JavaScript filesfound in the directory, such as placement of the files in the order:C.js, A.js, B.js.

In an embodiment, the directive information may be provided as one ormore sets of name/value pairs. For example, the JavaScript ObjectNotation (JSON) may be used to indicate name/value pairs and simplearrays in the directive information. Continuing with the example, forthe following directive information:

“{Mode: {“DEV”, “DEBUG”}, Path: {“B.js”, “A.js”}”

the directive information has the name value pairs of Mode=DEV andMode=DEBUG, and Path=B.js and Path=A.js. The directive information inthe example may be placed in any data structure. For example, an arraymay be created with the Mode array containing DEV and DEBUG.

The directive may begin with one or more characters or symbols todesignate the line as a directive in the source file. For example,directives may begin with //# and can be either single line ormultiline. In a preferred embodiment, the directive may begin with acomment symbol (e.g. //) that is not recognized by the JavaScriptcompiler or interpreter and a pound sign (e.g. #) to recognize thecommented text as a directive. The JavaScript may then be compiled orinterpreted without preprocessing if necessary because the directiveinformation is commented out and/or the directive information may remainin the preprocessed file for debugging purposes.

An “include” directive may include another source file at the directivelocation. The include directive may allow a user to separate source codeinto as many files as desired and serve it all as one file in the exactorder desired. The “include” directive enables a user to put the entirecontents of one file inside another file, not just before or after thefile. It may be desirable to use the “include” directive to put theentire contents of one file inside another file at the position wherethe include directive is placed in the source file and provide morefunctionality than simply indicating a dependency between files. Forexample, the “include” directive below may be in a JavaScript file andindicates that a mode “DEV” will include a file in the JavaScript filefor mode “DEV” with a file path “B.js”:

//#include {modes: [“DEV”], path: “B.js”}.

The directive information of the mode “DEV” and path “B.js” is providedwith the directive in the example.

An “if” directive is a conditional directive and enables a user tooutput an entire block of source code when a condition is met. The “if”directive may enable a user to output a block of code in the modesdesired and omit the code when other modes are designated. For example,an “if” directive below may include the “function testFoo( ){ }” in theJavaScript file version for a mode “TEST” with the following:

//# if {modes: [“TEST”]{    function testFoo( ){ }” //#endif.

A mode provides the ability to designate source files or portions offiles for a context to be written in the same file. A user may definedirectives and modes for any purpose. The directives and directiveinformation may be parsed and extracted from the original source and thedirectives may be used to generate multiple copies of the source (e.g.one for each mode).

A version of the JavaScript source file for the mode may be created(106). The version of the JavaScript source code file may haveJavaScript from the original JavaScript source file and at least aportion of the JavaScript file that may be identified in the directiveinformation (e.g. data provided with the directive). The mode may beused with a directive in order to change the output based on thecontext.

Context may include, but is not limited to, debug, development,production, test, performance test, or any other circumstances and/orexpected usage for which the JavaScript may be written. A mode mayspecify whether the output should be compressed. For example,compression may involve removing all white space and comments from theJavaScript file.

Modes may indicate a state in implementation for the code, such asdevelopment, production, beta testing, and testing modes. For example, adevelopment mode may be used for adding debugging code, a productionmode may be optimized and compressed for use by an end user, and atesting mode may be used when running automated tests, generallyexposing private data for the test case to verify. One or moreJavaScript files may be created from the original JavaScript source codefile.

In an embodiment, the resulting JavaScript file may concatenate the modeand the original JavaScript filename together to form the filename forthe version of the JavaScript source code file. For example, thefilename for a source code file “B.js” with mode “DEV” may be“B_DEV.js.”

In another embodiment, the mode may be for a particular tenant of amulti-tenant database. The mode may be used to specify JavaScript to beadded to a JavaScript file for a particular tenant. When a user and/or aclient is identified as associated with a particular tenant (e.g. with atenant primary key), then a particular portion of a JavaScript fileand/or entire JavaScript file may be served to the client.

Metadata may be associated with the version of the JavaScript file(108). Metadata may be included with the directive information and/orgenerated during preprocessing of the JavaScript source code file.Metadata may include, but is not limited to, the following: directiveinformation, timestamp for creation of file or portion of a file, datapath and filename for JavaScript file or portion of JavaScript file,label information, security information, personalization, one or moreServlets associated with JavaScript, or any other metadata used forserving a webpage at a client device. For example, the metadata mayinclude information on what portions of JavaScript have been alteredsince the last preprocessing occurred. A Servlet is a Java languageclass that can respond to Hypertext Transfer Protocol (HTTP) requests.The Servlet may enable adding dynamic content to a webpage.

A “label” directive may indicate a portion of a webpage that may need tobe altered or dynamic. For example, the “label” directive may be used tosupport localization. Localization is the adaption of a portion of thewebpage for a user in a non-native environment, especially other nationsor cultures. An example of a label directive is as follows:

//# label {section: “buttons”, param: “go”}.

With the label directive, in the example, a button on a webpage with thetext description of “go” may be altered in accordance with the languageof other nations and/or accepted text for a particular culture. Thedirective information of the section and param may be stored as metadatafor the label directive. Metadata associated with the label directivemay provide the additional localization information to enable changingthe text description of the button (e.g. param) on a webpage served tothe client. In the example, the param directive information may serve asa parameter for an object or element on the HTML webpage and the HTMLmay be generated on-the fly.

Labels directives may be used for a variety of purposes including, butnot limited to, formatting of dates, formatting of numbers, formattingnames, and/or any other customization for a webpage. The associatedmetadata may be stored during preprocessing and available for laterretrieval. The associated metadata may be stored in properties files forlater instantiation of classes that utilize the information. Forexample, the metadata may be placed into a Java .properties file and maybe used by an instantiation of a class that provides access to theproperties in the file. The metadata may be stored with methodsincluding, but not limited to, the following: an XML file, a database, astatic mapping, or any other implementation that enables storage ofdata.

Although various directives are shown as examples throughout, those withskill in the art will recognize that are a variety of directives thatmay be created and configured to provide a plurality of versions ofJavaScript, a plurality of versions of webpages, and/or portions of awebpages. Although various implementations are provided throughout thatutilize the Java programming language, HTML, Java Servlets, Java ServletPages (JSP), and XML, those with skill in the art will recognize thatvarious programming languages may be used to implement a JavaScriptpreprocessor.

FIG. 2 illustrates an example of a simplified flow diagram for animplementation of adding directives for JavaScript files directly intosource code. The associated metadata may have been identified duringpreprocessing, as described with FIG. 1 by receiving a JavaScript sourcefile for preprocessing (100), parsing the JavaScript file (102),identifying directive information for a directive within the JavaScriptfile (104), and associating metadata with the version of the JavaScriptfile (108). The associated metadata may be stored in memory or any othercollection of data for later use.

Metadata associated with a preprocessed directive may be retrieved(200). The preprocessed directive may be a directive from the originalJavaScript source code file. The metadata may be associated with theversion of the JavaScript source file, associated with the particularpreprocessed directive from the original JavaScript source code,associated with a group of one or more JavaScript files, the contextualmode, and/or any other association that can be communicated with theJavaScript file and/or directive or any combination thereof.

In an embodiment, a data structure may be used to allow for retrieval ofthe metadata. For example, the associated metadata may have been storedin a properties file as name/value pairs. A Java class may beinstantiated and the attributes may be assigned the metadata values inproperties file. In an embodiment, the name/value pairs may be retrievedwith an implementation of a data structure that utilizes a hashfunction, such as a hash table or hash map, and stored in memory.

In a preferred embodiment, the web server may provide access to amapping of the associations of metadata established duringpreprocessing. For example, upon startup of the web server, the Java Mapclass may be created using the properties file with the associatedmetadata and a static reference to the Java Map class may be provided. Astatic reference may exist throughout the execution of a softwareprogram and the existence of the static may not depend on theinstantiation of a particular class. In another example, the web servermay instantiate a Java Map class to hold the associations of metadata.The associations may be placed in to memory with the instantiation ofthe Java Map class while the web server is executing and the metadatamay be retrieved upon request. The mapping may be available in memory atthe web server to allow for access of the associated metadata for thepreprocessed directive.

A request may be received for associated metadata (202). A request forthe associated metadata may be made with a method or function call, useof a script, a Servlet, JSP, and/or any other method for accessing themetadata using webpages. The metadata associated with a preprocesseddirective and/or a preprocessed JavaScript file may be requested. Forexample, metadata associated with the version of the JavaScript sourcefile may be requested, such as a uniform resource locator (URL) or atimestamp. A method or function may be called to retrieve metadata. Forexample, a method may be called to retrieve a URL for a portion of theJavaScript included in a version of a JavaScript file to ensure that themost recent version of the portion of JavaScript is received.

The method may be called when a user requests a page that utilizes themetadata to create and serve the webpage to the user. In an embodiment,one or more static methods may be available to access the associatedmetadata. A static method may exist throughout the execution of asoftware program and the existence of the static may not depend on theinstantiation of a particular class.

In an embodiment, a Servlet may be put in the header of the webpage andthe Servlet may send requests to receive the metadata associated withthe preprocessed directive. In another example, a script may be placedon a webpage with a “script” tag that calls methods to request metadataassociated with a preprocessed directive. The mapping may be availablein memory at the web server to allow for access of the associatedmetadata for the preprocessed directive with the requests. For example,the file path for the most recent versions of the JavaScript files maybe accessed for each group of JavaScript files associated with andcreated for a particular version of a JavaScript file duringpreprocessing.

In another example, localization information may be requested. Forexample, the language for a button provided by a directive in theoriginal JavaScript may be requested and metadata associated with thepreprocessed directive may be requested. The localization informationmay be requested using a call to a Servlet in the header of the HTML.For example, the header of the HTML may be as follows:

<head> <script src=/jslabels/foo.js /> </head>and the //#label {section: “buttons”, param: “go”} in a version of theoriginal JavaScript file may be replaced with the appropriate buttonwith the appropriate text for the nation or culture of the user and/orspecified by the user.

At least a portion of markup language for a web page may be generated inaccordance with metadata (204). For example, a URL for a particular modewith the most up-to-date version may be placed within the HTML for awebpage in accordance with the metadata. In another example, theappropriate button type may be presented on the webpage in accordancewith localization information for the user.

The directives may be used to personalize a webpage for a particulartenant with the associated metadata. In another embodiment, a parameterfor a configurable directive may be a tenant identifier from amulti-tenant database. The metadata associated with file and the tenantidentifier may be retrieved from a database and/or a file system. In anembodiment, the metadata may be JavaScript, a portion of a webpage,scripts, or tasks that may be personalized for the tenant. Althoughpersonalization is provided by way of example on the tenant level, thosewith skill in the art will recognize that any level of granularity maybe used to personalize a webpage (e.g. by user, group of users, etc.).

FIG. 3 illustrates an example of a block diagram for an implementationof adding directives for JavaScript files directly into source code. AScript 300 may be used to indicate the JavaScript Source File 302 to bepreprocessed by the Preprocessor 304. In a preferred embodiment, a Javaclass may be used to run the preprocessing and indicate the JavaScriptsource file(s) for preprocessing. The Preprocessor 304 may use a Parser308 to identify Configurable Directives 1 . . . N 310 within theJavaScript Source File 302.

The Configurable Directive 310 may be recognized by the Parser 308 inaccordance with the Configurable Directive Definition 1 . . . N 312. TheConfigurable Directive Definition 1 . . . N may indicate the syntax andsemantics of a directive in a JavaScript Source File 302. For example,the Configurable Directive Definition 1 . . . N 312 may indicate whattokens (e.g. words and/or expressions) to be found by the lexer of theParser 308 and the grouping of tokens to be recognized in the grammar ofthe Parser 308 for the directive. The Preprocessor 304 may create one ormore versions of JavaScript File(s) 314 in accordance with ConfigurableDirectives 310 in the JavaScript Source File 302.

The Configurable Directive 310 may indicate a Mode and one or morePortion(s) of JavaScript 324 to be added to the version of theJavaScript Source Code File 306. A different JavaScript File 314 may becreated for each mode found in the Configurable Directives 310 of theJavaScript Source File 302. The JavaScript File(s) 1 . . . N 314 may beused on Webpages 316 served to the Client Device 318 using the WebServer 320 over the Network 322. The JavaScript may be compiled at thebrowser on the Client Device 318 and used to display the Webpage 316 onthe Client Device 318.

In an embodiment, the Web Server 320 may run a script to have Metadata324 identified during the preprocessing to be available in memory. TheMetadata 324 may be identified when parsing the JavaScript Source CodeFile 306 with the Parser 308. For example, a mapping of URLs toJavaScript for a particular group of JavaScript files created andidentified during preprocessing may be placed into memory to handlerequests for the URL to reach the particular group of JavaScript files.In another example, a mapping of text written in each language may bemapped to an enumerated type for the language and/or country identifiedduring preprocessing may be placed into memory to handle requests forthe appropriate text for a button on a webpage.

In one or more embodiment, a Database 326 may be used to store Metadata324. A database may be any collection of data including, but not limitedto, a relational database, an object-oriented database, a multi-tenantdatabase, a file system, or any other collection of data. In anembodiment, metadata for a tenant, such as JavaScript and/or HTML for atenant may be stored in the Database 326, and may be retrieved asMetadata 324 associated with the JavaScript Source Code File 306 and atenant identifier. A tenant identifier may be a primary key that allowsfor retrieval of the Metadata 324 for a particular tenant.

FIG. 4 illustrates an example of a flow diagram for an implementation ofadding directives for JavaScript files directly into source code.Information may be received on a JavaScript source code file forpreprocessing (400). The Script 300 may be used to begin preprocessingof JavaScript files. In an embodiment, the Script 300 is a Java programthat begins preprocessing and may indicate the JavaScript Source Code306 file for preprocessing. The Script 300 may provide a relative filepath or file path for the JavaScript source code file to thePreprocessor 304.

The JavaScript source code file may be parsed to identify one or moreconfigurable directives (402). The configurable directive may indicateone or more JavaScript files or portions of JavaScript code that may bewritten to a version of the JavaScript files produced by the JavaScriptSource Code 306 and the Preprocessor 304. The configurable directive inthe JavaScript Source Code 306 file may have been configured by a userto have name/value pairs. For example, name/value pairs may be indicatedin the text of the directive:

//#include {Mode: [“TEST”], path: “B.js.”}

with the Mode=“TEST” and the path=“B.js.”

The configurable directive in the JavaScript Source Code 306 mayindicate a relative file path or a file path to a JavaScript file, adirectory, or any other file that may indicate one or more JavaScriptfiles to include in a version of the JavaScript source code file. Forexample, “path:B.js” may indicate that the file “B.js” in the currentdirectory be included in the version of the JavaScript file. In anembodiment, the configurable directive may be configured to identify afilepath to an XML file with groups of JavaScript files to include in aversion of the JavaScript source code file.

The configurable directive may indicate modes and/or conditions thatmust be met for placement of the JavaScript code in a version of aJavaScript source code file produced with the JavaScript Source Code 306and the Preprocessor 304. For example, “Mode: TEST” may indicate thatthe following source code or file may be placed in a version of theJavaScript Source Code 306 file for “TEST.” In another example, acondition may need to be met and a BOOLEAN value of either true or falsewill dictate whether the JavaScript is included in the version of theJavaScript file.

Versions of JavaScript files may be created with the JavaScript sourcecode file for modes found in the one or more configurable directives(404). A version of a JavaScript file may be created for each mode foundin the one or more configurable directives in the JavaScript Source Code306 file. In an embodiment, the versions of JavaScript files may only beupdated with the underlying source files included with the configurabledirectives that have changed or been accessed, such that the timedatestamp for the file has been altered.

The Configurable Directive(s) 310 in the JavaScript Source Code 306 filemay indicate metadata to be associated with the version of theJavaScript file generated by the preprocessing and/or the ConfigurableDirective(s) 310. In an embodiment, the timedate for the version of theJavaScript file generated during preprocessing and the timedate for allfiles used to create the version of the JavaScript file may beassociated with the version of the JavaScript file. In anotherembodiment, metadata with URLs for the JavaScript files that were usedto create a version of the JavaScript file for a mode may be associatedwith the version of the JavaScript File. In another embodiment,localization information for a portion of JavaScript may be associatedwith the preprocessed directive in the original JavaScript source codefile.

A mapping may be created for retrieval of the metadata (406). Themetadata may be identified and/or generated during preprocessing. Forexample, the mapping may include the latest modification timestampassociated with each portion of JavaScript 324 used to create a versionof a JavaScript File 314 for the JavaScript Source Code File 306. Themapping may include the configured name/value pairs identified in theConfigurable Directive 310. The mapping may include localizationinformation for a portion of the Webpage 316 generated with theJavaScript.

The metadata may be associated with the Configurable Directive 310, theversion of the JavaScript File 314, a portion of JavaScript 324 used tocreate the JavaScript File 314, the original JavaScript Source Code File306, or any other association that aids in retrieval of the metadataused to create WebPages 316 on the Client Device 318.

A script may be executed to put the metadata mapping in memory (408). Inan embodiment, the script is run by the Web Server 320 to ensure thatthe mapping is in memory for retrieval of the metadata when the WebPages316 is served to the Client Device 318. For example, the script mayinstantiate Java classes to ensure that the mapping is in memory and canreceive requests for the metadata.

A request may be received for a JavaScript file with a Mode (410). In anembodiment, static methods are provided for retrieval of the correctJavaScript file name for a particular mode. In a preferred embodiment, aSingleton design pattern is used for the methods used to retrieve themetadata (e.g. the URL for a JavaScript file with a particular Mode) toensure that there is a single mapping of the metadata and that there isa single point of access to the mapping. An example of a request madefor a JavaScript file with a particular Mode in a JavaServer Page (JSP)page is, follows:

<% JavaScriptURLs.getURL(“B”, Mode.PROD) %>.

Continuing with the example, the method “getURL” of the “JavaScriptURL”class may retrieve the file path for the file having the JavaScript for“B” and the mode “PROD” indicated with the enumerated type “Mode.PROD.”“B” in the example may be a JavaScript Source Code File name or a Groupname included in a JavaScript Source Code File. The metadata of the URLfor B may be associated with the JavaScript Source Code File Name and/orthe Group indicated in the JavaScript Source Code File Name.

The URL may be retrieved for the JavaScript File with the mode (412).Continuing with the example above, the URL returned may be as follows“/js/[timestamp]/B.js”, where “timestamp” is the most recent timestampwhen the JavaScript file was altered, accessed, or touched.

The Webpage may be generated for display to the user using theJavaScript with the Mode (414). The retrieved URL may be place in theheader of the html file generated and served to the client. For example,the URL retrieved may be placed in the header as follows:

<head><script src=“/js/1234/B.js”/></head>.

In an embodiment, a webpage may be designated as a webpage never tocache and/or to rarely cache. When a call is made to retrieve a URL(e.g. getURL), a new modification date may be indicated and the functionmay return the new file name with the new modified name. For example,the modification indicator in the present example could have incrementedfrom “1233” to “1234” in the present example. In another example, arefresh may be requested within the HTML or performed manually with theweb browser, and a modified file with a new filename may be retrieved.

Groups

In one or more embodiments, any number of JavaScript file(s) may beassigned to a group. Metadata may be retrieved from a source file andmay be used to keep track of dependencies and/or ordering of files toensure groups are served in the proper order and invalidate groups whenthe group or portion of the group is updated.

In one or more embodiments, a JavaScript library may be created that maynot automatically include every file at once. One or more JavaScriptfiles may be joined into a single file and the single file may be servedup dynamically through the use of a Servlet. The inventors noteperformance issues at both the server side and client side that mayoccur with an approach that indiscriminately adds new files to a singleJavaScript file and includes the single concatenated JavaScript filethroughout (e.g. served with every page on a website).

In one or more embodiments, a library of JavaScript files may be splitup into groups. The groups may provide the ability to serve multipleJavaScript files with nice code separation and still serve the files upin a group as one file to minimize server roundtrips. In an embodiment,a main group with a majority of the JavaScript may be included on everypage.

Groups of JavaScript files may be generated into a static file. AJavaScript library may handle labels and interdependencies and thegenerated files may be compressed in production mode to reduce theirsize. For example, to add a new JavaScript file, a determination may bemade as to where the file is used. If the file is used only on one ortwo pages for one or two features, then the file can be placed in a newgroup and the group may be included on that particular webpage.

Embodiments may utilize Extensible Markup Language (XML) to define andadd a new group. For example, an xml file may be used to add a new group(or use the appropriate group). Individual files or entire directoriesmay be specified to be a part of your group. For example, a group may bespecified in an xml, as follows:

<group name=“Reports”>  <file path=“common/reporting/Reports.js”/></group> <group name=“Calendar”>  <dir path=“core/calendar”/> </group>

Continuing with the example, the group may be included on a page. In anembodiment, JavaScript groups may automatically refresh in developermode such that if you change a file and then refresh the page, then theJavaScript will be updated as well. For example, if a new file or changeto the XML file is made, then a user may run an Ant™ task to generatethe JavaScript and restart the web server and/or use the “Refresh JS”button in the development header.

In another embodiment, an addition of a file to a JavaScript librarydirectory may not result in the file being pulled in automatically toevery page. In one or more embodiments, a new file may be added to aJavaScript library with the creation of a JavaScript group or theaddition of the file to an existing group. For example, if you have aJavaScript group by the name of MyGroup, then you can use the“includeScript” tag from the Salesforce Visualforce™ markup in your pageas follows:

<apex:includeScript value=“/jslibrary/MyGroup”/>.

System Overview

FIG. 5 illustrates a block diagram of an environment 710 wherein anon-demand database service might be used. Environment 710 may includeuser systems 712, network 714, system 716, processor system 717,application platform 718, network interface 720, tenant data storage722, system data storage 724, program code 726, and process space 728.In other embodiments, environment 710 may not have all of the componentslisted and/or may have other elements instead of, or in addition to,those listed above.

Environment 710 is an environment in which an on-demand database serviceexists. User system 712 may be any machine or system that is used by auser to access a database user system. For example, any of user systems712 can be a handheld computing device, a mobile phone, a laptopcomputer, a work station, and/or a network of computing devices. Asillustrated in FIG. 5 (and in more detail in FIG. 6) user systems 712might interact via a network 714 with an on-demand database service,which is system 716.

An on-demand database service, such as system 716, is a database systemthat is made available to outside users that do not need to necessarilybe concerned with building and/or maintaining the database system, butinstead may be available for their use when the users need the databasesystem (e.g., on the demand of the users). Some on-demand databaseservices may store information from one or more tenants stored intotables of a common database image to form a multi-tenant database system(MTS). Accordingly, “on-demand database service 716” and “system 716”will be used interchangeably herein. A database image may include one ormore database objects. A relational database management system (RDMS) orthe equivalent may execute storage and retrieval of information againstthe database object(s). Application platform 718 may be a framework thatallows the applications of system 716 to run, such as the hardwareand/or software, e.g., the operating system. In an embodiment, on-demanddatabase service 716 may include an application platform 718 thatenables creation, managing and executing one or more applicationsdeveloped by the provider of the on-demand database service, usersaccessing the on-demand database service via user systems 712, or thirdparty application developers accessing the on-demand database servicevia user systems 712.

The users of user systems 712 may differ in their respective capacities,and the capacity of a particular user system 712 might be entirelydetermined by permissions (permission levels) for the current user. Forexample, where a salesperson is using a particular user system 712 tointeract with system 716, that user system has the capacities allottedto that salesperson. However, while an administrator is using that usersystem to interact with system 716, that user system has the capacitiesallotted to that administrator. In systems with a hierarchical rolemodel, users at one permission level may have access to applications,data, and database information accessible by a lower permission leveluser, but may not have access to certain applications, databaseinformation, and data accessible by a user at a higher permission level.Thus, different users will have different capabilities with regard toaccessing and modifying application and database information, dependingon a user's security or permission level.

Network 714 is any network or combination of networks of devices thatcommunicate with one another. For example, network 714 can be any one orany combination of a LAN (local area network), WAN (wide area network),telephone network, wireless network, point-to-point network, starnetwork, token ring network, hub network, or other appropriateconfiguration. As the most common type of computer network in currentuse is a TCP/IP (Transfer Control Protocol and Internet Protocol)network, such as the global internetwork of networks often referred toas the “Internet” with a capital “I,” that network will be used in manyof the examples herein. However, it should be understood that thenetworks that the present invention might use are not so limited,although TCP/IP is a frequently implemented protocol.

User systems 712 might communicate with system 716 using TCP/IP and, ata higher network level, use other common Internet protocols tocommunicate, such as HTTP, FTP, AFS, WAP, etc. In an example where HTTPis used, user system 712 might include an HTTP client commonly referredto as a “browser” for sending and receiving HTTP messages to and from anHTTP server at system 716. Such an HTTP server might be implemented asthe sole network interface between system 716 and network 714, but othertechniques might be used as well or instead. In some implementations,the interface between system 716 and network 714 includes load sharingfunctionality, such as round-robin HTTP request distributors to balanceloads and distribute incoming HTTP requests evenly over a plurality ofservers. At least as for the users that are accessing that server, eachof the plurality of servers has access to the MTS′ data; however, otheralternative configurations may be used instead.

In one embodiment, system 716, shown in FIG. 5, implements a web-basedcustomer relationship management (CRM) system. For example, in oneembodiment, system 716 includes application servers configured toimplement and execute CRM software applications as well as providerelated data, code, forms, webpages and other information to and fromuser systems 712 and to store to, and retrieve from, a database systemrelated data, objects, and Webpage content. With a multi-tenant system,data for multiple tenants may be stored in the same physical databaseobject, however, tenant data typically is arranged so that data of onetenant is kept logically separate from that of other tenants so that onetenant does not have access to another tenant's data, unless such datais expressly shared. In certain embodiments, system 716 implementsapplications other than, or in addition to, a CRM application. Forexample, system 716 may provide tenant access to multiple hosted(standard and custom) applications, including a CRM application. User(or third party developer) applications, which may or may not includeCRM, may be supported by the application platform 718, which managescreation, storage of the applications into one or more database objectsand executing of the applications in a virtual machine in the processspace of the system 716.

One arrangement for elements of system 716 is shown in FIG. 5, includinga network interface 720, application platform 718, tenant data storage722 for tenant data 723, system data storage 724 for system data 725accessible to system 716 and possibly multiple tenants, program code 726for implementing various functions of system 716, and a process space728 for executing MTS system processes and tenant-specific processes,such as running applications as part of an application hosting service.Additional processes that may execute on system 716 include databaseindexing processes.

Several elements in the system shown in FIG. 5 include conventional,well-known elements that are explained only briefly here. For example,each user system 712 could include a desktop personal computer,workstation, laptop, PDA, cell phone, or any wireless access protocol(WAP) enabled device or any other computing device capable ofinterfacing directly or indirectly to the Internet or other networkconnection. User system 712 typically runs an HTTP client, e.g., abrowsing program, such as Microsoft's Internet Explorer browser,Netscape's Navigator browser, Opera's browser, or a WAP-enabled browserin the case of a cell phone, PDA or other wireless device, or the like,allowing a user (e.g., subscriber of the multi-tenant database system)of user system 712 to access, process and view information, pages andapplications available to it from system 716 over network 714. Each usersystem 712 also typically includes one or more user interface devices,such as a keyboard, a mouse, trackball, touch pad, touch screen, pen orthe like, for interacting with a graphical user interface (GUI) providedby the browser on a display (e.g., a monitor screen, LCD display, etc.)in conjunction with pages, forms, applications and other informationprovided by system 716 or other systems or servers. For example, theuser interface device can be used to access data and applications hostedby system 716, and to perform searches on stored data, and otherwiseallow a user to interact with various GUI pages that may be presented toa user. As discussed above, embodiments are suitable for use with theInternet, which refers to a specific global internetwork of networks.However, it should be understood that other networks can be used insteadof the Internet, such as an intranet, an extranet, a virtual privatenetwork (VPN), a non-TCP/IP based network, any LAN or WAN or the like.

According to one embodiment, each user system 712 and all of itscomponents are operator configurable using applications, such as abrowser, including computer code run using a central processing unitsuch as an Intel Pentium® processor or the like. Similarly, system 716(and additional instances of an MTS, where more than one is present) andall of their components might be operator configurable usingapplication(s) including computer code to run using a central processingunit such as processor system 717, which may include an Intel Pentium®processor or the like, and/or multiple processor units. A computerprogram product embodiment includes a machine-readable storage medium(media) having instructions stored thereon/in which can be used toprogram a computer to perform any of the processes of the embodimentsdescribed herein. Computer code for operating and configuring system 716to intercommunicate and to process webpages, applications and other dataand media content as described herein are preferably downloaded andstored on a hard disk, but the entire program code, or portions thereof,may also be stored in any other volatile or non-volatile memory mediumor device as is well known, such as a ROM or RAM, or provided on anymedia capable of storing program code, such as any type of rotatingmedia including floppy disks, optical discs, digital versatile disk(DVD), compact disk (CD), microdrive, and magneto-optical disks, andmagnetic or optical cards, nanosystems (including molecular memory ICs),or any type of media or device suitable for storing instructions and/ordata. Additionally, the entire program code, or portions thereof, may betransmitted and downloaded from a software source over a transmissionmedium, e.g., over the Internet, or from another server, as is wellknown, or transmitted over any other conventional network connection asis well known (e.g., extranet, VPN, LAN, etc.) using any communicationmedium and protocols (e.g., TCP/IP, HTTP, HTTPS, Ethernet, etc.) as arewell known. It will also be appreciated that computer code forimplementing embodiments of the present invention can be implemented inany programming language that can be executed on a client system and/orserver or server system such as, for example, C, C++, HTML, any othermarkup language, Java™, JavaScript, ActiveX, any other scriptinglanguage, such as VBScript, Flex, and many other programming languagesas are well known may be used. (Java™ is a trademark of SunMicrosystems, Inc.).

According to one embodiment, each system 716 is configured to providewebpages, forms, applications, data and media content to user (client)systems 712 to support the access by user systems 712 as tenants ofsystem 716. As such, system 716 provides security mechanisms to keepeach tenant's data separate unless the data is shared. If more than oneMTS is used, they may be located in close proximity to one another(e.g., in a server farm located in a single building or campus), or theymay be distributed at locations remote from one another (e.g., one ormore servers located in city A and one or more servers located in cityB). As used herein, each MTS could include one or more logically and/orphysically connected servers distributed locally or across one or moregeographic locations. Additionally, the term “server” is meant toinclude a computer system, including processing hardware and processspace(s), and an associated storage system and database application(e.g., OODBMS or RDBMS) as is well known in the art. It should also beunderstood that “server system” and “server” are often usedinterchangeably herein. Similarly, the database object described hereincan be implemented as single databases, a distributed database, acollection of distributed databases, a database with redundant online oroffline backups or other redundancies, etc., and might include adistributed database or storage network and associated processingintelligence.

FIG. 6 also illustrates environment 710. However, in FIG. 6 elements ofsystem 716 and various interconnections in an embodiment are furtherillustrated. FIG. 6 shows that user system 712 may include processorsystem 712A, memory system 712B, input system 712C, and output system712D. FIG. 6 shows network 714 and system 716. FIG. 6 also shows thatsystem 716 may include tenant data storage 722, tenant data 723, systemdata storage 724, system data 725, User Interface (UI) 830, ApplicationProgram Interface (API) 832, PL/SOQL 834, save routines 836, applicationsetup mechanism 838, applications servers 8001-800N, system processspace 802, tenant process spaces 804, tenant management process space810, tenant storage area 812, user storage 814, and application metadata816. In other embodiments, environment 710 may not have the sameelements as those listed above and/or may have other elements insteadof, or in addition to, those listed above.

User system 712, network 714, system 716, tenant data storage 722, andsystem data storage 724 were discussed above in FIG. 5. Regarding usersystem 712, processor system 712A may be any combination of one or moreprocessors. Memory system 712B may be any combination of one or morememory devices, short term, and/or long term memory. Input system 712Cmay be any combination of input devices, such as one or more keyboards,mice, trackballs, scanners, cameras, and/or interfaces to networks.Output system 712D may be any combination of output devices, such as oneor more monitors, printers, and/or interfaces to networks. As shown byFIG. 6, system 716 may include a network interface 720 (of FIG. 5)implemented as a set of HTTP application servers 800, an applicationplatform 718, tenant data storage 722, and system data storage 724. Alsoshown is system process space 802, including individual tenant processspaces 804 and a tenant management process space 810. Each applicationserver 800 may be configured to tenant data storage 722 and the tenantdata 723 therein, and system data storage 724 and the system data 725therein to serve requests of user systems 712. The tenant data 723 mightbe divided into individual tenant storage areas 812, which can be eithera physical arrangement and/or a logical arrangement of data. Within eachtenant storage area 812, user storage 814 and application metadata 816might be similarly allocated for each user. For example, a copy of auser's most recently used (MRU) items might be stored to user storage814. Similarly, a copy of MRU items for an entire organization that is atenant might be stored to tenant storage area 812. A UI 830 provides auser interface and an API 832 provides an application programmerinterface to system 716 resident processes to users and/or developers atuser systems 712. The tenant data and the system data may be stored invarious databases, such as one or more Oracle™ databases.

Application platform 718 includes an application setup mechanism 838that supports application developers' creation and management ofapplications, which may be saved as metadata into tenant data storage722 by save routines 836 for execution by subscribers as one or moretenant process spaces 804 managed by tenant management process 810 forexample. Invocations to such applications may be coded using PL/SOQL 834that provides a programming language style interface extension to API832. Invocations to applications may be detected by one or more systemprocesses, which manages retrieving application metadata 816 for thesubscriber making the invocation and executing the metadata as anapplication in a virtual machine.

Each application server 800 may be communicably coupled to databasesystems, e.g., having access to system data 725 and tenant data 723, viaa different network connection. For example, one application server 8001might be coupled via the network 714 (e.g., the Internet), anotherapplication server 800N-1 might be coupled via a direct network link,and another application server 800N might be coupled by yet a differentnetwork connection. Transfer Control Protocol and Internet Protocol(TCP/IP) are typical protocols for communicating between applicationservers 800 and the database system. However, it will be apparent to oneskilled in the art that other transport protocols may be used tooptimize the system depending on the network interconnect used.

In certain embodiments, each application server 800 is configured tohandle requests for any user associated with any organization that is atenant. Because it is desirable to be able to add and remove applicationservers from the server pool at any time for any reason, there ispreferably no server affinity for a user and/or organization to aspecific application server 800. In one embodiment, therefore, aninterface system implementing a load balancing function (e.g., an F5Big-IP load balancer) is communicably coupled between the applicationservers 800 and the user systems 712 to distribute requests to theapplication servers 800. In one embodiment, the load balancer uses aleast connections algorithm to route user requests to the applicationservers 800. Other examples of load balancing algorithms, such as roundrobin and observed response time, also can be used. For example, incertain embodiments, three consecutive requests from the same user couldhit three different application servers 800, and three requests fromdifferent users could hit the same application server 800. In thismanner, system 716 is multi-tenant, wherein system 716 handles storageof, and access to, different objects, data and applications acrossdisparate users and organizations.

As an example of storage, one tenant might be a company that employs asales force where each salesperson uses system 716 to manage their salesprocess. Thus, a user might maintain contact data, leads data, customerfollow-up data, performance data, goals and progress data, etc., allapplicable to that user's personal sales process (e.g., in tenant datastorage 722). In an example of a MTS arrangement, since all of the dataand the applications to access, view, modify, report, transmit,calculate, etc., can be maintained and accessed by a user system havingnothing more than network access, the user can manage his or her salesefforts and cycles from any of many different user systems. For example,if a salesperson is visiting a customer and the customer has Internetaccess in their lobby, the salesperson can obtain critical updates as tothat customer while waiting for the customer to arrive in the lobby.

While each user's data might be separate from other users' dataregardless of the employers of each user, some data might beorganization-wide data shared or accessible by a plurality of users orall of the users for a given organization that is a tenant. Thus, theremight be some data structures managed by system 716 that are allocatedat the tenant level while other data structures might be managed at theuser level. Because an MTS might support multiple tenants includingpossible competitors, the MTS should have security protocols that keepdata, applications, and application use separate. Also, because manytenants may opt for access to an MTS rather than maintain their ownsystem, redundancy, up-time, and backup are additional functions thatmay be implemented in the MTS. In addition to user-specific data andtenant specific data, system 716 might also maintain system level datausable by multiple tenants or other data. Such system level data mightinclude industry reports, news, postings, and the like that are sharableamong tenants.

In certain embodiments, user systems 712 (which may be client systems)communicate with application servers 800 to request and updatesystem-level and tenant-level data from system 716 that may requiresending one or more queries to tenant data storage 722 and/or systemdata storage 724. System 716 (e.g., an application server 700 in system716) automatically generates one or more SQL statements (e.g., one ormore SQL queries) that are designed to access the desired information.System data storage 724 may generate query plans to access the requesteddata from the database.

Each database can generally be viewed as a collection of objects, suchas a set of logical tables, containing data fitted into predefinedcategories. A “table” is one representation of a data object, and may beused herein to simplify the conceptual description of objects and customobjects according to the present invention. It should be understood that“table” and “object” may be used interchangeably herein. Each tablegenerally contains one or more data categories logically arranged ascolumns or fields in a viewable schema. Each row or record of a tablecontains an instance of data for each category defined by the fields.For example, a CRM database may include a table that describes acustomer with fields for basic contact information such as name,address, phone number, fax number, etc. Another table might describe apurchase order, including fields for information such as customer,product, sale price, date, etc. In some multi-tenant database systems,standard entity tables might be provided for use by all tenants. For CRMdatabase applications, such standard entities might include tables forAccount, Contact, Lead, and Opportunity data, each containingpre-defined fields. It should be understood that the word “entity” mayalso be used interchangeably herein with “object” and “table”.

In some multi-tenant database systems, tenants may be allowed to createand store custom objects, or they may be allowed to customize standardentities or objects, for example by creating custom fields for standardobjects, including custom index fields. In certain embodiments, forexample, all custom entity data rows are stored in a single multi-tenantphysical table, which may contain multiple logical tables perorganization. It is transparent to customers that their multiple“tables” are in fact stored in one large table or that their data may bestored in the same table as the data of other customers.

Any suitable programming language can be used to implement the routinesof particular embodiments including C, C++, Java, assembly language,etc. Different programming techniques can be employed such as proceduralor object oriented. The routines can execute on a single processingdevice or multiple processors. Although the steps, operations, orcomputations may be presented in a specific order, this order may bechanged in different particular embodiments. In some particularembodiments, multiple steps shown as sequential in this specificationcan be performed at the same time.

Particular embodiments may be implemented in a computer-readable storagemedium for use by or in connection with the instruction executionsystem, apparatus, system, or device. Particular embodiments can beimplemented in the form of control logic in software or hardware or acombination of both. The control logic, when executed by one or moreprocessors, may be operable to perform that which is described inparticular embodiments.

A “processor” includes any suitable hardware and/or software system,mechanism or component that processes data, signals or otherinformation. A processor can include a system with a general-purposecentral processing unit, multiple processing units, dedicated circuitryfor achieving functionality, or other systems. Processing need not belimited to a geographic location, or have temporal limitations. Forexample, a processor can perform its functions in “real time,”“offline,” in a “batch mode,” etc. Portions of processing can beperformed at different times and at different locations, by different(or the same) processing systems. A computer may be any processor incommunication with a memory. The memory may be any suitableprocessor-readable storage medium, such as random-access memory (RAM),read-only memory (ROM), magnetic or optical disk, or other tangiblemedia suitable for storing instructions for execution by the processor.

Particular embodiments may be implemented by using a programmed generalpurpose digital computer, by using application specific integratedcircuits, programmable logic devices, field programmable gate arrays,optical, chemical, biological, quantum or nanoengineered systems,components and mechanisms may be used. In general, the functions ofparticular embodiments can be achieved by any means as is known in theart. Distributed, networked systems, components, and/or circuits can beused. Communication, or transfer, of data may be wired, wireless, or byany other means.

It will also be appreciated that one or more of the elements depicted inthe drawings/figures can also be implemented in a more separated orintegrated manner, or even removed or rendered as inoperable in certaincases, as is useful in accordance with a particular application. It isalso within the spirit and scope to implement a program or code that canbe stored in a machine-readable medium to permit a computer to performany of the methods described above.

As used in the description herein and throughout the claims that follow,“a”, “an”, and “the” includes plural references unless the contextclearly dictates otherwise. Also, as used in the description herein andthroughout the claims that follow, the meaning of “in” includes “in” and“on” unless the context clearly dictates otherwise.

While the invention has been described by way of example and in terms ofthe specific embodiments, it is to be understood that the invention isnot limited to the disclosed embodiments. To the contrary, it isintended to cover various modifications and similar arrangements aswould be apparent to those skilled in the art. Therefore, the scope ofthe appended claims should be accorded the broadest interpretation so asto encompass all such modifications and similar arrangements.

The invention claimed is:
 1. A method, comprising: receiving, at apreprocessor, a source file for preprocessing, wherein the source fileis written in a client-side scripting language; parsing, at thepreprocessor, the source file; identifying, at the preprocessor, adirective within the source file; associating, at the preprocessor,metadata with the directive during the preprocessing such that thedirective is a preprocessed directive, wherein the metadata comprises:information regarding which portions of the source file have beenaltered since a last preprocessing of the source file has occurred, andat least a portion of the source file in the client-side scriptinglanguage for generating at least a portion of markup language for a webpage to be served to a client device using a webserver; retrieving,during the preprocessing, only the metadata associated with thepreprocessed directive in the source file from a database system suchthat the entire source file is not retrieved; storing, during thepreprocessing, the metadata associated with the preprocessed directivein a hash table; receiving a request to access metadata associated withthe preprocessed directive in the source file from the hash table; andgenerating the at least the portion of markup language for the web pageto be served to the client device in accordance with the metadataassociated with the preprocessed directive in response to the request.2. The method of claim 1, further comprising: creating, during thepreprocessing and prior to receiving the request, a mapping for thestored metadata associated with the preprocessed directive.
 3. Themethod of claim 1, wherein the metadata associated with the directive islocalization information.
 4. The method of claim 1, wherein thedirective is a label directive and the source file is a JavaScript file.5. The method of claim 1, further comprising: generating HTML inaccordance with localization information provided in metadata associatedwith the preprocessed directive.
 6. The method of claim 1, furthercomprising: receiving a request to access metadata associated with thepreprocessed directive using at least one of a Servlet, a static method,and a script.
 7. The method of claim 1, wherein the metadata associatedwith the directive is a set of name and value pairs provided in thesource file.
 8. A non-transitory computer-readable storage medium havingone or more instructions thereon, the instructions when executed by oneor more processors causing the one or more processors to carry out:receiving a source file for preprocessing, wherein the source file iswritten in a client-side scripting language; parsing the source file;identifying a directive within the source file; associating metadatawith the directive during the preprocessing such that the directive is apreprocessed directive, wherein the metadata comprises: informationregarding which portions of the source file have been altered since alast preprocessing of the source file has occurred, and at least aportion of the source file in the client-side scripting language forgenerating at least a portion of markup language for a web page to beserved to a client device using a webserver; retrieving, during thepreprocessing, only the metadata associated with the preprocesseddirective in the source file such that the entire source file is notretrieved; storing, during the preprocessing, the metadata associatedwith the preprocessed directive in a hash table; creating, during thepreprocessing, a mapping for the stored metadata associated with thepreprocessed directive; receiving, after the parsing, identifying,associating, retrieving, storing, and creating, a request to accessmetadata associated with the preprocessed directive in the JavaScriptsource file; and generating the at least the portion of markup languagefor the web page to be served to the client device in accordance withthe metadata associated with the preprocessed directive from the hashtable according to the mapping in response to the request.
 9. Thenon-transitory computer-readable storage medium of claim 8, wherein themetadata associated with the directive is localization information. 10.The non-transitory computer-readable storage medium of claim 8, whereinthe directive is a label directive and the source file is a JavaScriptfile.
 11. The non-transitory computer-readable storage medium of claim8, the instructions when executed by one or more processors causing theone or more processors to carry out: generating HTML in accordance withlocalization information provided in metadata associated with thepreprocessed directive.
 12. The non-transitory computer-readable storagemedium of claim 8, the instructions when executed by one or moreprocessors causing the one or more processors to carry out: receiving arequest to access metadata associated with the preprocessed directiveusing at least one of a Servlet, a static method, and a script.
 13. Asystem for adding directives for JavaScript files directly into sourcecode, the system comprising: a processor; and one or more storedsequences of instructions which, when executed by the processor, causethe processor to carry out: receiving a source file for preprocessing,wherein the source file is written in a client-side scripting language;parsing the source file; identifying a directive within the source file;associating metadata with the directive during the preprocessing suchthat the directive is a preprocessed directive, wherein the metadatacomprises: information regarding which portions of the source file havebeen altered since a last preprocessing of the source file has occurred,and at least a portion of the source file in the client-side scriptinglanguage for generating at least a portion of markup language for a webpage to be served to a client device using a webserver; retrieving,during the preprocessing, only the metadata associated with thepreprocessed directive in the source file such that the entire sourcefile is not retrieved; storing, during the preprocessing, the metadataassociated with the preprocessed directive in a hash table; creating,during the preprocessing, a mapping for the stored metadata associatedwith the preprocessed directive; receiving, after the parsing,identifying, associating, retrieving, storing, and creating, a requestto access the metadata associated with the preprocessed directive in thesource file; and generating the at least the portion of markup languagefor the web page to be served to the client device in accordance withthe metadata associated with the preprocessed directive from the hashtable according to the mapping in response to the request.
 14. Thesystem of claim 13, wherein the metadata associated with the directiveis localization information.
 15. The system of claim 13, wherein thedirective is a label directive and the source file is a JavaScript file.16. The system of claim 13, wherein the one or more stored sequences ofinstructions which, when executed by the processor, cause the processorto further carry out: generating HTML in accordance with localizationinformation provided in metadata associated with the preprocesseddirective.
 17. The system of claim 13, wherein the one or more storedsequences of instructions which, when executed by the processor, causethe processor to further carry out: receiving a request to accessmetadata associated with the preprocessed directive using at least oneof a Servlet, a static method, and a script.
 18. The system of claim 13,wherein the one or more stored sequences of instructions which, whenexecuted by the processor, cause the processor to further carry out:receiving a request to access metadata associated with the preprocesseddirective using at least one of a Servlet, a static method, and ascript.
 19. The method of claim 1, wherein the directive comprises dataon at least a portion of a client-side scripting language file and atleast one mode, wherein the method further comprises creating, afteridentifying the directive, a version of the source file for each of theat least one mode, wherein the version of the source file comprises thesource code from the source file and the at least a portion of theclient-side scripting language file, and wherein the associatingincludes associating the metadata with the version of the source filefor each of the at least one mode.
 20. The method of claim 19, whereinthe metadata associated with the version of the source file includes atime date for the version of the source file generated during thepreprocessing.